Guide Density onboarding with background history sync#11
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the Density plugin onboarding flow around first-time setup.
onboarding_statusso agents can track that job and tell the user when full supported local history is ready.Why
First-time setup should get users to useful local answers quickly without hiding that deeper local history is still loading. The agent needs a durable status surface so follow-up turns can report background progress instead of guessing from Parquet timestamps.
Notes
Specific-location onboarding should be enabled after DensityCo/density-cli#40 lands, is released, and the plugin pins a runtime containing
density onboard scope/sync --scope.The background job uses the existing CLI historical export path, so Data Access API observation requests keep the existing UTC calendar-month chunking behavior.
Validation
npm test